Ignorant question but why is the config_proc_macro test trying to remove the ci-integration.exe binary file on windows? I didn't find anywhere in the repository a call to remove files in the out dir...

Ignorant question but why is the config_proc_macro test trying to remove the ci-integration.exe binary file on windows? I didn't find anywhere in the repository a call to remove files in the out dir...

Looking at the logs, that errors during the cargo build step, following:

• The action runs cargo run --bin ci-integration build-and-test so target/debug/ci-integration.exe is built
• That binary then runs cargo build --locked . with a different env (RUSTFLAGS='-D warnings') so it triggers a rebuild of target/debug/ci-integration.exe

So I think that's why it tries to remove it (because it's rebuilding) but not why that would cause an error. Unless Windows doesn't like it when a process deletes the file that spawned it

Interesting. But then why is it only an issue on Windows CI?

Interesting. But then why is it only an issue on Windows CI?

I'm starting to suspect my hunch

... Windows doesn't like it when a process deletes the file that spawned it

is correct, but I don't know enough about Windows internals (nor handy access to a Windows machine) to be certain.

Writing down the process:

1. We run cargo run --bin ci-integration build-and-test
2. It sets the environment flags, including RUSTFLAGS="-D warnings"
3. We run cargo build --locked
4. We run cargo test
5. We go into the config_proc_macro folder and run cargo build --locked. At this step it fails. But it's being run with the same environment variables. Hence my confusion.

Writing down the process:

1. We run cargo run --bin ci-integration build-and-test

2. It sets the environment flags, including RUSTFLAGS="-D warnings"

3. We run cargo build --locked

I think this is where we error out (some extra logging/reporting of the args being run in the error might help locate it), I see in the logs:

1. A bunch of download+compile logs ending with Running target\debug\ci-integration.exe build-and-test (i.e. building that before running it)
2. The output of rustc -vV and cargo -v, that ends with See 'cargo help <command>' for more information on a specific command. (because I think the original script has a bug, and that should be cargo -V i.e. cargo --version, so it prints the cargo help output)
3. A bunch of download+compile logs from the cargo build step, and then the error

Since there's no Finished dev profile .... output I don't think it ever finishes the first cargo build

Oh I think you're right. Hum... Gonna need to think about how to solve that...

Is the CI status report broken?

Ah no, github actions files were broken. Yeay status reporting. ^^'

(Will review this weekend, didn't get to it last weekend)

No hurry, I still need to find a way to prevent cargo to rebuild ci-integration. Currently trying with exclude but that creates other issues. It's super annoying that we can't tell cargo "ignore this project if you rebuild".

Finally made it work! \o/

Ready for review now @jieyouxu when you have time. ;)